Problem Note 52862: "Failed to deploy the file 'full-path-to-SAS-program-file' (9)" occurs when you perform a batch job deployment for SAS® Data Integration Studio jobs
When you deploy SAS Data Integration Studio jobs using the command-line batch deployment tool, a message similar to the following might be displayed in the console window:
Failed to deploy the file full-path-to-the-SAS-program-file (9).
The error message can occur for the following reasons:
- The ID that is used to deploy the file does not have Write access to the target location.
- A problem occurs when the job code is created.
- The job was previously deployed and the Deployed Job metadata object already exists.
The message might be incorrect when the last reason above is true. In fact, the SAS program file might have been properly deployed. You can confirm this by verifying the datetime stamp on the deployed file.
The batch job deployment tool does not fully support redeployment of jobs. If a Deployed Job metadata object with the same name already exists in the metadata, the deployment process cannot replace or update the existing object. As long as the current deployment settings, specifically the deployment directory that is being used, match the prior deployment settings, redeployment is possible. If the deployment settings have changed, the redeployment does not update the metadata to reflect the new deployment directory.
If the job has been redeployed to a new deployment directory, you need to synchronize the metadata settings. One option is to open SAS Data Integration Studio, select delete the deployed job object, and redeploy the job object to the new location.
CAUTION: Be aware that deleting the original deployed job object breaks any associations the object might have with other pre-existing SAS Data Integration Studio jobs.
Operating System and Release Information
SAS System | SAS Data Integration Studio | Microsoft® Windows® for x64 | 4.7 | 4.9 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows 8 Enterprise x64 | 4.7 | 4.9 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows 8 Pro x64 | 4.7 | 4.9 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows 8.1 Enterprise 32-bit | 4.7 | 4.9 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows 8.1 Enterprise x64 | 4.7 | 4.9 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows 8.1 Pro | 4.7 | 4.9 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows 8.1 Pro 32-bit | 4.7 | 4.9 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows Server 2008 R2 | 4.7 | 4.9 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows Server 2008 for x64 | 4.7 | 4.9 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows Server 2012 Datacenter | 4.7 | 4.9 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows Server 2012 R2 Datacenter | 4.7 | 4.9 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows Server 2012 R2 Std | 4.7 | 4.9 | 9.4 TS1M0 | 9.4 TS1M2 |
Microsoft Windows Server 2012 Std | 4.7 | 4.9 | 9.4 TS1M0 | 9.4 TS1M2 |
Windows 7 Enterprise x64 | 4.7 | 4.9 | 9.4 TS1M0 | 9.4 TS1M2 |
Windows 7 Professional x64 | 4.7 | 4.9 | 9.4 TS1M0 | 9.4 TS1M2 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
When deploying SAS Data Integration Studio jobs with the command-line batch deployment tool, the error might occur for one of three reasons. In some instances, the message is actually incorrect and the job has been redeployed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2014-06-25 10:38:01 |
Date Created: | 2014-04-30 15:46:59 |